-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix cert-manager injection target #1106
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR @PaulFarver, I think this is the fix for #1046 that I couldn't replicate. Have you tested the updated behaviour? Could you also please add an entry to the CHANGELOG under [UNRELEASED]
?
Right... I tested it, but now I get the following 😅
So I'll change it to target the certificate resource with the other annotation |
Now it's tested and working :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor nit.
Co-authored-by: Steve Hipwell <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@stevehipwell When do you usually release? |
Ahh... I see it now. I've created a PR for it at #1111 |
@stevehipwell thanks for maintaining this chart 🎉
When running with
.Values.admissionController.certManager.enabled
we get the following error in our cert-manager-cainjector:Taking a look at the templates, it looks like the annotation expects a reference to a certificate, but gets a reference to a secret. We can fix that with the following, based on the documentation here: https://cert-manager.io/docs/concepts/ca-injector/#injecting-ca-data-from-a-secret-resource